Systems and methods for a check / exception station

ABSTRACT

A system for a check and exception center may include a holding area, a manual section, a distribution section. The manual section may include a plurality of handling areas each enabled for pill counting, pharmacist verification, exception handling, or combinations thereof. The distribution section may be disposed proximate the manual section, and may include a robot and a scanner. The robot may be adapted to pick a container from the holding area and to move the container to the scanner for scanning. The robot may also be further adapted to direct the container to a first handling area of the plurality of handling areas. At least one handling area of the plurality of handling areas may include an evaluation device, and the evaluation device may be configured determine a second handling area being enabled for a determined action with respect to the container, determine workloads of the first handling area and the second handling area; and select a handling area from the first handling area and the second handling area with a lower workload to receive the container.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/803,009, filed on Jul. 17, 2015; said application claims priority toU.S. Provisional Patent Application No. 62/028,211, filed Jul. 23, 2014.The entire disclosures of U.S. application Ser. 14/803,009, and U.S.Provisional Patent Application No. 62/028,211 are hereby incorporatedherein by reference.

FIELD

The present application relates generally to the technical field ofautomated filling centers. In a specific example, the presentapplication may relate to a high volume fulfillment center, e.g., a highvolume pharmacy and to systems and devices used in filling prescriptionsand prescription orders at a high volume pharmacy.

BACKGROUND

A high-volume pharmacy may process and fill a large number ofprescriptions and prescription orders. Automated systems may be used bya high volume pharmacy to process and fulfill prescriptions.

Frequently, more than one prescription drug is required to complete aprescription order. Portions of the prescription order may be fulfilledin different areas of the high-volume pharmacy. After fulfillment, thefulfilled prescriptions may be gathered into a complete prescriptionorder for shipping.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example system, according to an exampleembodiment;

FIG. 2 is a block diagram of an example order processing device that maybe deployed within the system of FIG. 1, according to an exampleembodiment;

FIG. 3A is a schematic plan view of a check and exception center thatmay be deployed within the system of FIG. 1, according to an exampleembodiment;

FIG. 3B is a schematic elevation view of the check and exception centerthat may be deployed within the system of FIG. 1, according to anexample embodiment;

FIG. 4 is a schematic perspective view of a handling area of a check andexception center according to an example embodiment;

FIG. 5 is a block diagram of a control unit that may be deployed withinthe manual fill center of FIGS. 3A and 3B, according to an exampleembodiment;

FIG. 6 is a block diagram of a container status subsystem that may bedeployed within the control unit of FIG. 5, according to an exampleembodiment;

FIG. 7 is a block diagram of resource management subsystem that may bedeployed within the control unit of FIG. 5, according to an exampleembodiment;

FIG. 8 is an example process flow illustrating a method of pharmacistchecking, exception handling and pill counting, according to an exampleembodiment; and

FIG. 9 is a block diagram of a machine in the example form of a computersystem within which a set of instructions for causing the machine toperform any one or more of the methodologies discussed herein may beexecuted or stored.

DETAILED DESCRIPTION

Example systems and methods for operation of a check/exception station(e.g., in a pharmacy) are described. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of example embodiments. Itwill be evident, however, to one of ordinary skill in the art that theseembodiments may be practiced without these specific details.

Generally, a prescription order is generated for a high volume pharmacy.The prescription order may include more than one prescription drug forfulfillment. Each prescription drug in a prescription order is an ordercomponent of the prescription order. Generally, the order components arepill bottles or other containers and packaging having a quantity of aprescription drug therein.

The prescription drugs may be dispensed at various sections of the highvolume pharmacy. After dispensing, some containers may be reviewed by apharmacist for proper pill count, exception handling, prescriptionverification, and the like. As a non-limiting example, fulfilledprescriptions may be manually reviewed and/or verified by a pharmacist,as may be required by state or local law. The pharmacist may review,verify, and/or evaluate drug quantity, drug strength, and/or druginteraction concerns, or otherwise perform pharmacist services. Thepharmacist may also handle containers which have been flagged as anexception, such as containers with unreadable labels, containers forwhich the associated prescription order has been cancelled, containerswith defects, and the like. In an example embodiment, the manual reviewcan be performed at the manual station.

FIG. 1 is a block diagram of an example system 100, according to anexample embodiment. While the system 100 is generally described as beingdeployed in a high volume pharmacy (e.g., a mail order pharmacy, adirect delivery pharmacy, an automated pharmacy, and the like), thesystem 100 may otherwise be deployed. The system 100 may include anorder processing device 102 in communication with a benefit managerdevice 106 over a network 104. Additional devices which may be incommunication with the benefit manager device 106 and/or the orderprocessing device 102 over network 104 include: database(s) 108 whichmay store one or more than one of order data 110, member data 112,claims data 114, drug data 116, prescription data 118, and plan sponsordata 120; pallet sizing and pucking device(s) 122; loading device(s)124; inspect device(s) 126; unit of use device(s) 128; automateddispensing device(s) 130; manual fulfillment device(s) 132; reviewdevice(s) 134; imaging device(s) 136; cap device(s) 138; accumulationdevice(s) 140; literature device(s) 141; packing device(s) 142; and unitof use packing device(s) 144. The system 100 may also include additionaldevices, which may communicate with each other over network 104 ordirectly.

The order processing device 102 may receive information aboutprescriptions being filled at a pharmacy in which the order processingdevice 102 is deployed. In general, the order processing device 102 is adevice located within or otherwise associated with a pharmacy locationto enable fulfillment of a prescription by dispensing prescriptiondrugs. In some embodiments, the order processing device 102 may be adevice separate from a pharmacy that enables communication with otherdevices located within a pharmacy. For example, the order processingdevice 102 may be in communication with another order processing device102 and/or other devices 122-144 located with a pharmacy. In someembodiments, an external pharmacy order processing device 102 may havelimited functionality (e.g., as operated by a patient requestingfulfillment of a prescription drug) when an internal pharmacy orderprocessing device 102 may have greater functionality (e.g., as operatedby a pharmacy).

The order processing device 102 may track a prescription order as it isfulfilled. A prescription order may include one or more than oneprescription to be filled by the pharmacy. The order processing device102 may make pharmacy routing decisions and/or order consolidationdecisions for a prescription order. The pharmacy routing decisionsinclude what device or devices in the pharmacy are responsible forfilling at least a portion of the prescription order, where the orderconsolidation decisions include whether portions of a prescription orderor multiple prescription orders should be shipped together for a patientor a patient family. The order processing device 102 may operate on itsown or in combination with the benefit manager device 106. The orderprocessing device 102 may track and/or schedule the literature or otherpaperwork associated with each order or multiple prescription ordersthat are being shipped together.

Examples of the devices 102, 106 include a set-top box (STB), a receivercard, a mobile telephone, a personal digital assistant (PDA), a displaydevice, a portable gaming unit, a tablet, and a computing system;however other devices may also be used. For example, the devices 102,106 may include a mobile electronic device, such an IPHONE or IPADdevice by Apple, Inc., mobile electronic devices powered by ANDROID byGoogle, Inc., and a BLACKBERRY device by Blackberry Limited. The orderprocessing device 102 may also include other computing devices, such asdesktop computing devices, notebook computing devices, netbook computingdevices, gaming devices, servers, and the like. The device 102 mayinclude circuitry, a processor, a memory to store data and instructions,and communication functionality. Other types of electronic devices thatcan use rules and instructions to execute various functions may also beused.

Examples of the network 104 include Mobile Communications (GSM) network,a code division multiple access (CDMA) network, 3rd GenerationPartnership Project (3GPP), an Internet Protocol (IP) network, aWireless Application Protocol (WAP) network, a WiFi network, or an IEEE802.11 standards network, as well as various combinations thereof. Thenetwork 104 may include optical communications. The network 104 may be alocal area network or a global communication network, such as theInternet. Other conventional and/or later developed wired and wirelessnetworks may also be used. In some embodiments, the network 104 mayinclude a prescribing network such as the electronic prescribing networkoperated by Surescripts of Arlington, Va.

The benefit manager device 106 is a device operated by an entity atleast partially responsible for creation and/or management of thepharmacy or drug benefit. While this benefit manager operating thebenefit manager device 106 is typically a pharmacy benefit manager(PBM), other entities may operate the benefit manager device 106 eitheron behalf of themselves, the PBM, or another entity. For example, thebenefit manager may be operated by a health plan, a retail pharmacychain, a drug wholesaler, a data analytics or other type ofsoftware-related company, or the like. In some embodiments, a PBM thatprovides the pharmacy benefit may also provide one or more than oneadditional benefits including a medical or health benefit, a dentalbenefit, a vision benefit, a wellness benefit, a radiology benefit, apet care benefit, an insurance benefit, a long term care benefit, anursing home benefit, and the like. The PBM may, in addition to its PBMoperations, operate one or more than one pharmacy. The pharmacies may beretail pharmacies, mail order pharmacies, or otherwise.

Some of the operations of the PBM that operates the benefit managerdevice 106 may include the following. A member (or a person on behalf ofthe member) of a pharmacy benefit plan administered by or through thePBM attempts to obtain a prescription drug at a retail pharmacy locationwhere the member can obtain drugs in a physical store from a pharmacistor pharmacist technician, or in some instances through mail order drugdelivery from a mail order pharmacy location. The member may also obtaina prescription drug directly or indirectly through the use of a machine,such as a kiosk, vending unit, mobile electronic device, or a differenttype of mechanical, electrical, electronic communication device and/orcomputing device.

The member may have a co-pay for the prescription drug that reflects anamount of money that the member is responsible to pay the pharmacy forthe prescription drug. The money paid by the member to the pharmacy maycome from the personal funds of the member, a health savings account(HSA) of the member or the member's family, a health reimbursementarrangement (HRA) of the member or the member's family, a flexiblespending accounts (FSA) of the member or the member's family, or thelike. An employer of the member may directly or indirectly fund orreimburse the member or an account of the member for the co-pay.

The amount of the co-pay paid by the member may vary by the benefit planof a plan sponsor or client with the PBM. The member's co-pay may bebased on a flat co-pay (e.g., $10), co-insurance (e.g., 10%), and/or adeductible (e.g., for first $500 of annual prescription drug spend) forcertain prescription drugs, certain types and/or classes of prescriptiondrugs, and/or all prescription drugs.

In certain instances, the member may not pay the co-pay or may only payfor a portion of a co-pay for a prescription drug. For example, if theusual and customary cost for a generic version of a prescription drug is$4, and the member's flat co-pay is $20 for the prescription drug, themember may only pay $4 to receive the prescription drug. In anotherexample involving a worker's compensation claim, no co-pay may be due bythe member for the prescription drug. The co-pay may also vary based onthe delivery channel used to receive the prescription drug. For example,the co-pay for receiving prescription drug from a mail order pharmacylocation may be less than the co-pay for receiving prescription drugfrom a retail pharmacy location.

In conjunction with receiving the co-pay (if any) from the member anddispensing the prescription drug to the member, the pharmacy submits aclaim to the PBM for the prescription drug. The PBM may perform certainadjudication operations including verifying the eligibility of themember, reviewing an applicable formulary of the member to determineappropriate co-pay, coinsurance, and deductible for the prescriptiondrug, and performing a drug utilization review (DUR) on the member. ThePBM then provides a response to the pharmacy following performance of atleast some of the aforementioned operations. As part of theadjudication, the plan sponsor (or the PBM on behalf of the plansponsor) ultimately reimburses the pharmacy for filling the prescriptiondrug when the prescription drug was successfully adjudicated. Theaforementioned adjudication operations generally occur before the co-payis received and the prescription drug dispensed. However, the operationsmay occur simultaneously, substantially simultaneously, or in adifferent order. In addition, more or less adjudication operations maybe performed as at least part of the adjudication process.

The amount of reimbursement paid to the pharmacy by a plan sponsorand/or money paid by the member may be based at least in part on thetype of pharmacy network in which the pharmacy is included. Otherfactors may be used to determine the amount in addition to the type ofpharmacy network. For example, if the member pays the pharmacy for theprescription without using the prescription drug benefit provided by thebenefit manager, the amount of money paid by the member may be higherand the amount of money received by the pharmacy for dispensing theprescription drug and for the prescription drug itself may be higher.Some or all of the foregoing operations may be performed by executinginstructions on the benefit manager device 106 and/or an additionaldevice.

In some embodiments, at least some of the functionality of the orderprocessing device 102 may be included in the benefit manager device 106.The order processing device 102 may be in a client-server relationshipwith the benefit manager device 106, a peer-to-peer relationship withthe benefit manager device 106, or in a different type of relationshipwith the benefit manager device 106.

The order processing device 102 and/or the benefit manager device 106may be in communication directly (e.g., through local storage orpeer-to-peer connection(s)) and/or through the network 104 (e.g., in acloud configuration or software as a service) with a database 108 (e.g.,as may be retained in memory or otherwise). The database 108 may bedeployed on the order processing device 102, the benefit manager device106, on another device of the system 100, or otherwise. The database 108may store order data 110, member data 112, claims data 114, drug data116, prescription data 118, and/or plan sponsor data 120. Other data maybe stored in the database 108.

The order data 110 may include data related to the order ofprescriptions including the type (e.g., drug name and strength) andquantity of each prescription in a prescription order. The order data110 may also include data used for completion of the prescription, suchas prescription materials and/or the type and/or size of container inwhich the drug is or is preferably dispensed. In general, prescriptionmaterials are a type of order materials that include an electronic copyof information regarding the prescription drug for inclusion with orotherwise in conjunction with the fulfilled prescription. Theprescription materials may include electronic information regarding druginteraction warnings, recommended usage, possible side effects,expiration date, date of prescribing, or the like. The order data 110may be used by a high volume fulfillment center to fulfill a pharmacyorder.

In some embodiments, the order data 110 includes verificationinformation associated with fulfillment of the prescription in thepharmacy. For example, the order data 110 may include videos and/orimages taken of (i) the prescription drug prior to dispensing, duringdispensing, and/or after dispensing, (ii) the prescription container(e.g., a prescription bottle and sealing lid) used to contain theprescription drug prior to dispensing, during dispensing, and/or afterdispensing, (iii) the packaging and/or packaging materials used to shipor otherwise deliver the prescription drug prior to dispensing, duringdispensing, and/or after dispensing, and/or (iv) the fulfillment processwithin the pharmacy. Other type of verification information such as barcode data read from pallets used to transport prescriptions within thepharmacy may also be stored as order data 110.

The member data 112 includes information regarding the membersassociated with the benefit manager. The information stored as memberdata 112 may include personal information, personal health information,protected health information, and the like. Examples of the member data112 include name, address, telephone number, e-mail address,prescription drug history, and the like. The member data 112 may includea plan sponsor identifier that identifies the plan sponsor associatedwith the member and/or a member identifier that identifies the member tothe plan sponsor. The member data 112 may include a member identifierthat identifies the plan sponsor associated with the patient and/or apatient identifier that identifies the patient to the plan sponsor. Themember data 112 may also include, by way of example, dispensationpreferences such as type of label, type of cap, message preferences,language preferences, or the like.

The member data 112 may be accessed by various devices in the pharmacy,e.g., the high volume fulfillment center, to obtain information utilizedfor fulfillment and shipping of prescription orders. In someembodiments, an external order processing device 102 operated by or onbehalf of a member may have access to at least a portion of the memberdata 112 for review, verification, or other purposes.

In some embodiments, the member data 112 may include information forpersons who are patients of the pharmacy but are not members in abenefit plan being provided by the benefit manager. For example, thesepatients may obtain drug directly from the pharmacy, through a privatelabel service offered by the pharmacy, the high volume fulfillmentcenter, or otherwise. In general, the use of the terms member andpatient may be used interchangeably herein.

The claims data 114 includes information regarding pharmacy claimsadjudicated by the PBM under a drug benefit program provided by the PBMfor one, or more than one, plan sponsors. In general, the claims data114 includes an identification of the client that sponsors the drugbenefit program under which the claim is made, and/or the member thatpurchased the prescription drug giving rise to the claim, theprescription drug that was filled by the pharmacy (e.g., the nationaldrug code number), the dispensing date, generic indicator, GPI number,medication class, the cost of the prescription drug provided under thedrug benefit program, the copay/coinsurance amount, rebate information,and/or member eligibility. Additional information may be included.

In some embodiments, other types of claims beyond prescription drugclaims may be stored in the claims data 114. For example, medicalclaims, dental claims, wellness claims, or other type of healthcare-related claims for members may be stored as a portion of the claimsdata 114.

In some embodiments, the claims data 114 includes claims that identifythe members with whom the claims are associated. In some embodiments,the claims data 114 includes claims that have been de-identified (e.g.,associated with a unique identifier but not with a particular,identifiable member).

The drug data 116 may include drug name (e.g., technical name and/orcommon name), other names by which the drug is known by, activeingredients, an image of the drug (e.g., in pill form), and the like.The drug data 116 may include information associated with a singlemedication or multiple medications.

The prescription data 118 may include information regardingprescriptions that may be issued by prescribers on behalf of patients,who may be members of the drug benefit plan, for example to be filled bya pharmacy. Examples of the prescription data 118 include patient names,medication or treatment (such as lab tests), dosing information, and thelike. The prescriptions may be electronic prescriptions, paperprescriptions that have been scanned, or otherwise. In some embodiments,the dosing information reflects a frequency of use (e.g., once a day,twice a day, before each meal, etc.) and a duration of use (e.g., a fewdays, a week, a few weeks, a month, etc.).

In some embodiments, the order data 110 may be linked to associatedmember data 112, claims data 114, drug data 116, and/or prescriptiondata 118.

The plan sponsor data 120 includes information regarding the plansponsors of the benefit manager. Examples of the plan sponsor data 120include company name, company address, contact name, contact telephonenumber, contact e-mail address, and the like.

The order processing device 102 may direct at least some of theoperations of the devices 122-144, recited above. In some embodiments,operations performed by one of these devices 122-144 may be performedsequentially, or in parallel with the operations of another device asmay be coordinated by the order processing device 102. In someembodiments, the order processing device 102 tracks a prescription withthe pharmacy based on operations performed by one or more of the devices122-144.

In some embodiments, the system 100 may transport prescription drugcontainers (e.g., between one or more than one of the devices 122-144 inthe high volume fulfillment center) by use of pallets. The pallet sizingand pucking device 122 may configure pucks in a pallet. A pallet may bea transport structure for a number of prescription containers, and mayinclude a number of cavities. A puck may be placed in one or more thanone of the cavities in a pallet by the pallet sizing and pucking device122. A puck may include a receptacle sized and shaped to receive aprescription container. Such containers may be supported by the pucksduring carriage in the pallet and during movement through thefulfillment process. Different pucks may have differently sized andshaped receptacles to accommodate containers of differing sizes, as maybe appropriate for different prescriptions. Pucks allow thestandardization of equipment engaging differently sized drug containerssuch that some automated equipment can move the drug container bygripping the puck that is supporting the container and allow the use ofa standardized pallet that holds a plurality of pucks have a same outerdimension while having differently sized receptacles therein to holddifferently sized drug containers. The pucks may also operate to ensurethat a drug container is centered in a location on the pallet.

The arrangement of pucks in a pallet may be determined by the orderprocessing device 102 based on prescriptions which the order processingdevice 102 decides to launch. In general, prescription orders in theorder database 110 reside in one or more than one queues, and aregenerally launched in a first-in-first-out order. However, the orderprocessing device 102 may use logic and a variety of factors todetermine when and how prescriptions are to be launched. For example,some non-limiting factors which may alter the first-in-first-out orderof launching prescriptions in a pharmacy include the age of the order,whether the order required an outreach to a physician or some otherintervention, whether there are any performance guarantees with plansponsors or members, the available inventory of a given pharmaceuticalin view of existing prescriptions already launched which will requirethat pharmaceutical, the zip code to which the order will be shipped,the workload and volume of various parts of the pharmacy, whether validpaperwork for the order has been received, and/or similar orders for thesame pharmaceutical that are already to be launched. The logic may beimplemented directly in the pallet sizing and pucking device 122, in theorder processing device 102, in both devices 102, 122, or otherwise.Once a prescription is set to be launched, a puck suitable for theappropriate size of container for that prescription may be positioned ina pallet by a robotic arm or pickers. The pallet sizing and puckingdevice 122 may launch a pallet once pucks have been configured in thepallet.

The loading device 124 may load prescription containers into the puckson a pallet by a robotic arm, a pick and place mechanism, or the like.In one embodiment, the loading device 108 has robotic arms or pickers tograsp a prescription container and move it to and from a pallet. Theloading device 124 may also print a label which is appropriate for acontainer that is to be loaded onto the pallet, and apply the label tothe container. The pallet may be located on a conveyor assembly duringthese operations. In an example embodiment, the drug containers may bepositioned in the pucks by the loading device 124 prior to the pucksbeing placed in the pallet.

The inspect device 126 may verify that containers in a pallet arecorrectly labeled and in the correct spot on the pallet. The inspectdevice 126 may scan the label on one or more than one container on thepallet. Labels of containers may be scanned or imaged in full or in partby the inspect device 126. Such imaging may occur after the containerhas been lifted out of its puck by a robotic arm, picker, or the like,or may be otherwise scanned or imaged while retained in the puck. Insome embodiments, images and/or video captured by the inspect device 126may be stored in the database 108 as order data 110.

The unit of use device 128 may temporarily store, monitor, label and/ordispense unit of use products. In general, unit of use products areprescription drug products that may be delivered to a patient or memberwithout being repackaged at the pharmacy. These products may includepills in a container, pills in a blister pack, inhalers, and the like.Prescription drug products dispensed by the unit of use device 128 maybe packaged individually or collectively for shipping, or may be shippedin combination with other prescription drugs dispensed by other devicesin the high volume fulfillment center.

The automated dispensing device 130 may include one or more than onedevices that dispense prescription drugs or pharmaceuticals intoprescription containers in accordance with one or multiple prescriptionorders. In general, the automated dispensing device 130 may includemechanical and electronic components with, in some embodiments, softwareand/or logic to facilitate pharmaceutical dispensing that wouldotherwise be performed in a manual fashion by a pharmacist and/orpharmacist technician. For example, the automated dispensing device 130may include high volume fillers that fill a number of prescription drugtypes at a rapid rate and blister pack machines that dispense and packdrugs into a blister pack. Prescription drugs dispensed by the automateddispensing devices 130 may be packaged individually or collectively forshipping, or may be shipped in combination with other prescription drugsdispenses by other devices in the high volume fulfillment center.

The manual fulfillment device 132 may provide for manual fulfillment ofprescriptions. For example, the manual fulfillment device 132 mayreceive or obtain a container and enable fulfillment of the container bya pharmacist or pharmacy technician. In some embodiments, the manualfulfillment device 132 provides the filled container to another devicein the system 100. In an example embodiment, the container may be joinedwith other containers in a prescription order for a patient or member,e.g., on a pallet or at the accumulation device 140. In general, amanual fulfillment may include operations at least partially performedby a pharmacist or pharmacy technician. For example, a person mayretrieve a supply of the prescribed drug, may make an observation, maycount out a prescribed quantity of drugs and place them into aprescription container, or the like. Some portions of the manualfulfillment process may be automated by use of a machine. For example,counting of capsules, tablets, or pills may be at least partiallyautomated (e.g., through use of a pill counter). Prescription drugsdispensed by the manual fulfillment device 132 may be packagedindividually or collectively for shipping, or may be shipped incombination with other prescription drugs dispenses by other devices inthe high volume fulfillment center.

The review device 134 may process prescription containers to be reviewedby a pharmacist for proper pill count, exception handling, prescriptionverification, and the like. Fulfilled prescriptions may be manuallyreviewed and/or verified by a pharmacist, as may be required by state orlocal law. A pharmacist or other licensed pharmacy person who maydispense certain drugs in compliance with local and/or other laws mayoperate the review device 134 and visually inspect a prescriptioncontainer that has been filled with a prescription drug. The pharmacistmay review, verify, and/or evaluate drug quantity, drug strength, and/ordrug interaction concerns, or otherwise perform pharmacist services. Thepharmacist may also handle containers which have been flagged as anexception, such as containers with unreadable labels, containers forwhich the associated prescription order has been cancelled, containerswith defects, and the like. In an example embodiment, the manual reviewcan be performed at the manual station.

The imaging device 136 may image containers once they have been filledwith pharmaceuticals. The imaging device 136 may measure the fill heightof the pharmaceuticals in the container based on the obtained image todetermine if the container is filled to the correct height given thetype of pharmaceutical and the number of pills in the prescription.Images of the pills in the container may also be obtained to detect thesize of the pills themselves and markings thereon. The images may betransmitted to the order processing device 102, and/or stored in thedatabase 110 as part of the order data 110.

The cap device 138 may be used to cap or otherwise seal a prescriptioncontainer. In some embodiments, the cap device 138 may secure aprescription container with a type of cap in accordance with a patientpreference (e.g., a preference regarding child resistance), a plansponsor preference, a prescriber preference, or the like. The cap device138 may also etch a message into the cap or otherwise associate amessage into the cap, although this process may be performed by asubsequent device in the high volume fulfillment center.

The accumulation device 140 accumulates various containers ofprescription drugs in a prescription order. The accumulation device 140may accumulate prescription containers from various devices or areas ofthe pharmacy. For example, the accumulation device 140 may accumulateprescription containers from the unit of use device 128, the automateddispensing device 130, the manual fulfillment device 132, and the reviewdevice 134, at the high volume fulfillment center. The accumulationdevice 140 may be used to group the prescription containers prior toshipment to the member or otherwise.

In some embodiments, the literature device 141 folds or otherwiseprepares the literature for inclusion with a prescription drug order(e.g., in a shipping container). In some embodiments, the literaturedevice 141 that prints the literature may be separate from theliterature device that prepares the literature for inclusion with aprescription order.

The packing device 142 packages a prescription order in preparation forshipping the order. The packing device 142 may box, bag, or otherwisepackage the fulfilled prescription order for delivery. The packingdevice 142 may further place inserts, e.g., literature or other papers,into the packaging received from the literature device 141 or otherwise.For example, bulk prescription orders may be shipped in a box, whileother prescription orders may be shipped in a bag which may be a wrapseal bag. The packing device 142 may label the box or bag with theaddress and a recipient's name. The label may be printed and affixed tothe bag or box, be printed directly onto the bag or box, or otherwiseassociated with the bag or box. The packing device 142 may sort the boxor bag for mailing in an efficient manner (e.g., sort by deliveryaddress). The packing device 142 may include ice or temperaturesensitive elements for prescriptions which are to be kept within atemperature range during shipping in order to retain efficacy orotherwise. The ultimate package may then be shipped through postal mail,through a mail order delivery service that ships via group and/or air(e.g., UPS, FEDEX, or DHL), through delivery service, through a localdelivery service (e.g., a courier service), through a locker box at ashipping site (e.g., an AMAZON locker or a post office box), orotherwise.

The unit of use packing device 144 packages a unit of use prescriptionorder in preparation for shipping the order. The unit of use packingdevice 144 may include manual scanning of containers to be bagged forshipping to verify each container in the order. In an exampleembodiment, the manual scanning may be performed at a manual station.

While the system 100 in FIG. 1 is shown to include single devices 102,106, 122-144 multiple devices may be used. The devices 102, 106, 122-144may be the same type or model of device or may be different device typesor models. When multiple devices are present, the multiple devices maybe of the same device type or models or may be a different device typeor model. The types of devices 102, 106, 122-144 shown in FIG. 1 areexample devices. In other configurations of the system 100, lesser,additional, or different types of devices may be included.

Moreover, the system 100 shows a single network 104; however, multiplenetworks can be used. The multiple networks may communicate in serieswith each other to link the devices 102, 106, 122-144 or in parallel tolink the devices 102, 106, 122-144. Multiple devices may shareprocessing and/or memory resources. The devices 102, 106, 122-144 may belocated in the same area or in different locations. For example, thedevices 102, 106, 122-144 may be located in a building or set ofadjoining buildings. The devices 102, 106, 122-144 may be interconnected(e.g. by conveyors), networked, and/or otherwise in contact with oneanother or integrated with one another, e.g., at the high volumefulfillment center. In addition, the functionality of a device may besplit among a number of discrete devices and/or combined with otherdevices.

The system 100 may include a single database, or multiple databases,maintained by respective devices operated by or on behalf one or anumber of different persons and/or organizations. The communication mayoccur directly (e.g., through local storage) and/or through the network104 (e.g., in a cloud configuration or software-as-a-service) with adevice that stores a respective database.

FIG. 2 illustrates the order processing device 102, according to anexample embodiment. The order processing device 102 may be used by oneor more than one operator to generate prescription orders, make routingdecisions, make prescription order consolidation decisions, trackliterature within the system 100, and/or view order status and otherorder related information. For example, the prescription order may becomprised of order components. The order processing device 102 mayreceive instructions to fulfill an order without operator intervention.An order component may include a prescription drug fulfilled by use of acontainer through the system 100. The order processing device 102 maydirect an order component to the manual fulfillment device 132 and/or tothe review device 134, and direct other components to the automateddispensing device 130. The order processing device 102 may direct ordercomponents to the accumulation device 140 for aggregation beforeshipping. The order processing device 102 may direct the ordercomponents directly to the packing device 142 if the prescription orderdoes not require accumulation from various areas of the pharmacy forcompletion. The order processing device 102 may be deployed in thesystem 100, or may otherwise be used.

The order processing device 102 may include an order verificationsubsystem 202, an order control subsystem 204, and/or an order trackingsubsystem 206. Other subsystems may also be included in the orderprocessing device 102.

The order verification subsystem 202 may communicate with the benefitmanager device 106 to, verify the eligibility of the member, review theformulary to determine appropriate co-pay, coinsurance, and deductiblefor the prescription drug, and/or perform a DUR. Other communicationsbetween the order verification subsystem 202 and the benefit managerdevice 106 may be performed for a variety of purposes.

The order control subsystem 204 controls various movements of thecontainers and/or pallets along with various filling functions duringtheir progression through the system 100.

In some embodiments, the order control subsystem 204 may identify theprescribed drug in one or more than one prescription order as capable ofbeing fulfilled by the automated dispensing device 130. The ordercontrol subsystem 204 may determine which prescriptions are to belaunched, and may determine that a pallet of automated-fill containersis to be launched. The order control subsystem 204 may determine that anautomated-fill prescription of a specific pharmaceutical is to belaunched, and may examine a queue of orders awaiting fulfillment forother prescription orders which will be filled with the samepharmaceutical. The order control subsystem 204 may then launch orderswith similar automated-fill pharmaceutical needs together in a pallet tothe automated dispensing device 130.

In some embodiments, the order control subsystem 204 may identify theprescribed drug in one or more than one prescription order as needing tobe fulfilled manually and may direct the container or order component tothe manual fulfillment device 132 to achieve the manual fulfillment. Theorder control subsystem 204 may determine which prescriptions are to belaunched, and may determine that a pallet of manual-fill containers isto be launched. The order control subsystem 204 may determine that amanual-fill prescription of a specific pharmaceutical is to be launched,and may examine a queue of orders awaiting fulfillment for otherprescription orders which will be filled with the same pharmaceutical.The order control subsystem 204 may then launch orders with similarmanual-fill pharmaceutical needs together in a pallet to the manualfulfillment device 132. As the devices 122-144 may be interconnected bya system of conveyors or other container movement systems, the ordercontrol subsystem 204 may control various conveyors to deliver thepallet from the loading device 124 to the manual fulfillment device 132,for example.

The order tracking subsystem 206 may track a prescription order as itprogresses (or stops) toward fulfillment. The order tracking subsystem206 may track, record and/or update order history, order status, or thelike. The order tracking subsystem 206 may store data locally (e.g., ina memory) or as a portion of the order data 110 stored in the database108.

FIGS. 3A and 3B illustrate a check and exception center 300 according toan example embodiment. The review device 134 of FIG. 1 may be deployedin the system 100, or may be otherwise deployed. A check and exceptioncenter 300 may be deployed within a review device 134 of a pharmacy, andmay be operated by one or more pharmacists to manually handle certainprescription containers, or otherwise implemented and/or used. Certainprescription drugs that have been filled in a container 314 may bechecked by appropriate pharmacy personnel after filling but beforepackaging, for various reasons. The inspection could happen as a resultof a specific event occurring. As non-limiting examples, a wrong pillcolor detection may be made by an imaging device, or a wrong weightdetection may be made of the container 314, or a wrong pill depth may beidentified in the container 314. Alternatively, the inspection couldhappen as a result of general operations, such as manually checking andverifying one container 314 out of a predetermined number of filled pillcontainers 314. The check and exception center 300 may more accuratelyand quickly process prescription containers 314 subject tocheck/exception. The center 300 may balance the workload among differentpharmacy personnel, direct containers within the center 300 based onpersonnel expertise or anticipated amount of time to resolve current orprevious container with an issue, etc., as discussed in detail below.

The check and exception center 300 may include a control unit 302 whichmay operate at the direction of the order processing device 102. Thecheck and exception center 300 may also include a distribution section304 automating distribution of containers 314 for pharmacist handling,and a manual area 306 in which a pharmacist may perform prescriptionverification and exception handling actions on a container 314. Acontainer 314 may represent an order component of a prescription order.One or more than one order component may constitute a prescriptionorder. The check and exception center 300 may also include a feedconveyor 310 may supply containers 314 to a holding area 312, whichholds containers 314 awaiting action.

The distribution section 304 may include a robot 320 and a scanner 322.The robot 320 may be a SCARA robot or the like. In an exampleembodiment, a container 314 is picked by the robot 320 and distributedto the manual section 306. In some embodiments, the container 314 may beselected from other containers 314 as directed by the order processingdevice 102. A single container or multiple containers may be unloadedand distributed from the holding area 312. The robot 320 may be adaptedto pick the container 314 from the holding area 312 and scan thecontainer 314 via the scanner 322. The container 314 may be empty and/oruncapped, and/or may be filled and capped, or in any other state. Thecap may be screwed or twisted onto the top of the container 314, pressedonto to the top of the container 314, or otherwise. The scanner 322 mayinclude an image sensor that captures an image of the container 314 andlabel if available, and/or a barcode scanner. The robot 320 may beadapted to rotate the container 314 for the scanner 322 to obtainattributes, such as identifying data, from the label. Other devices mayadditionally or alternatively be used to remove the container 314 fromthe holding area 312, or the container 314 may be manually removed. Insome embodiments, an escapement may be used, and the container 314 maybe scanned while the container 314 is in the escapement. Thereby, therobot 320 may avoid rotating the container 314 in front of the scanner322 to scan the container 314.

The distribution section 304 may further include a delivery conveyor 330and a return conveyor 335. Delivery conveyor 330 may transport one ormore than one container 314 from the robot 320 to a handling area 340.Return conveyor 335 may transport one or more than one container 314from a handling area 340 to the robot 320. A single delivery conveyor330 or multiple delivery conveyors 330 may be incorporated into thecheck and exception center 300. A single return conveyor 335 or multiplereturn conveyors 335 may be incorporated into the check and exceptioncenter 300. As shown, the return conveyor 335 may be positioned belowthe delivery conveyor 330, and may run in the opposite directionthereof. However, in some embodiments, the return conveyor 335 may bepositioned alongside the delivery conveyor 330 or in other suitablelocations. The delivery conveyor 330 and the return conveyor 335 may bestraight, curved, or otherwise implemented according to the spaceavailable and location of the manual section 306.

The manual area 306 may include a handling area 340. One or multiplehandling areas 340 may be included in a single manual section 306. Forexample, FIG. 3A depicts six handling areas 340 in a single manualsection 306. The delivery conveyor 330 may deliver the containers 314 tothe handling area 340. In some embodiments, the delivery conveyor 330includes lanes 342 formed by guiderails 344. Each lane 342 may lead fromthe distribution section 304 to a specific handling area 340. Each lane342 may be associated with its own delivery conveyor 330, or a singledelivery conveyor 330 may be used for all lanes 342. The robot 320 maybe controllable by the control unit 302 to pick the containers 314 andplace them on the delivery conveyor 330 in the lane 342 leading to thehandling area 340 selected by the control unit 302. A handling area 340may be operated by a pharmacist for exception handling, sample counting,pharmacy verification, for other pharmacy-related operations, or thelike.

The return conveyor 335 receives the containers 314 at the handling area340 after handling by a pharmacist. As shown, return conveyor 335 mayinclude an inclined section 337 which leads back to the robot 320 in thedistribution section 304. The return conveyor 335 may include its ownholding area 312, which may be a different holding area 312 from thatused by the feed conveyor 310, or may be the same holding area 312. Onceback in the holding area 312, a container 314 may again be selected bythe robot 320, scanned, and again placed into a lane 342 as appropriatefor additional action. In some embodiments, the container 314 may beplaced on an outbound conveyor 345 by the robot 320. In someembodiments, the container 314 may be otherwise routed to the outboundconveyor 345.

FIG. 4 illustrates a handling area 340, according to an exampleembodiment. Each handling area 340 may include an evaluation device 405.An evaluation device 405 may include a display 410. The display 410 mayalso be an input device, although other forms of input devices such as amouse and/or keyboard and the like may also be used. The handling area340 may include a pill counter 415 for verifying the count of pills fromthe container 314. In some embodiments, pill counter 415 may be aKIRBYLESTER® model KL15 pill counter or the like. A physician ortechnician may merely pour the contents of a container 314 into the pillcounter 415, and the pill counter 415 verifies the number of pills whichare in the container 314. The evaluation device 405 and/the or pillcounter 415 may be in communication with the control unit 302. Theevaluation device 405 may also enable a pharmacist or technical toutilize the handling area 340 to perform certain functions associatedwith the filling and distribution of prescription drugs to a patient.The evaluation device 405 may allow a pharmacist or technician to selecta single or multiple actions to be taken at the handling area 340. Insome embodiments, upon enabling a handling area 340 for use, apharmacist may use the evaluation device 405 to initiate one or morethan one action including exception handling, sample counting, pharmacyverification, and the like at the handling area 340. Additionally, oncea container 314 is delivered to the handling area 340, the evaluationdevice 405 may inform the pharmacist to manually check the container 314and its contents. The evaluation device 405 may inform the pharmacist ortechnician as to why the container 314 was sent to the handling area340, and may instruct the pharmacist of the appropriate action to take.The evaluation device 405 may also display or otherwise provideverifying information, such as a copy of an electronic or paperprescription associated with the container 314, or information on apharmaceutical which should be present in the container 314. Theevaluation device 405 may further allow the pharmacist to makeinvestigative actions, such as review photos of video of the filling ofthe container 314, obtain information regarding which lot thepharmaceutical came from or which machines touched the container 314, orthe like. The pharmacist may also be able to confirm which actions wereperformed on the container 314. The handling area 340 is an examplehandling area that may be deployed in FIGS. 3A and 3B or otherwise.

FIG. 5 illustrates the control unit 302, according to an exampleembodiment. The control unit 302 may be deployed in the check andexception center 300, or may otherwise be deployed. The control unit 302may be communicatively connected to one or more than one components inthe distribution section 304 and/or the manual area 306, such as therobot 320, the evaluation device 405, and/or the pill counter 415. Thecontrol unit 302 may include a container status subsystem 502 and aresource management subsystem 504. The container status subsystem 502may enable the control unit 302 to determine an action called for withrespect to a container 314. The resource management subsystem 504 mayenable the control unit 302 to monitor workloads assigned to varioushandling areas 340.

FIG. 6 illustrates an example container status subsystem 502 that may bedeployed in the control unit 302, or may be otherwise deployed inanother system. One or more modules are communicatively coupled andincluded in the container status subsystem 502 to enable the containerstatus subsystem 502 to identify actions to be taken on a container 314.The modules of the container status subsystem 502 that may be includedare a communication module 602 and/or an identification module 604.Other modules may also be included.

In some embodiments, the modules of the container status subsystem 502may be distributed so that some of the modules are deployed in otherdevices within the pharmacy. In one embodiment, the modules are deployedin memory and executed by a processor coupled to the memory. Thefunctionality contained within the modules 602, 604 may be combined intoa lesser number of modules, further divided among a greater number ofmodules, or redistributed among existing modules. Other configurationsincluding the functionality of the modules 602, 604 may be used.

The communication module 602 may manage communication from and/or withinthe check and exception center 300. For example, the communicationmodule 602 may manage communications associated with the scanner 332 inorder to identify the container 314 that has been picked by the robot320. In some instances, the container 314 may have a label that isunreadable by the scanner 332, in which case the communication module602 may flag the container 314 as an exception. Presuming the scanner332 can read the label of container 314 and the container 314 can beidentified, the identification module 604 may determine the type ofaction to be taken on the container 314. For example, one or moreactions may be performed on the container 314, including but not limitedto exception handling, pharmacy verification, and pill counting. Theidentification module 604 may be in communication with the order controlsubsystem 204 to make such determination, or such functionality mayoccur only in either the order control subsystem 204 or inidentification module 604.

FIG. 7 illustrates an example resource management subsystem 504 that maybe deployed in the control unit 302, or may be otherwise deployed inanother system. One or more modules are communicatively coupled andincluded in the resource management subsystem 504. The modules of theresource management subsystem 504 that may be included are a handlingarea status module 702, a backlog module 704, an image confirmationmodule 706, and/or a robot module 708. Other modules may also beincluded.

In some embodiments, the modules of the resource management subsystem504 may be distributed so that some of the modules are deployed in otherdevices within the pharmacy. In one embodiment, the modules are deployedin memory and executed by a processor coupled to the memory. Thefunctionality contained within the modules 702-708 may be combined intoa lesser number of modules, further divided among a greater number ofmodules, or redistributed among existing modules. Other configurationsincluding the functionality of the modules 702-708 may be used.

The handling area module 702 may be in communication with evaluationdevice 405 at one or more than one of the handling areas 340. Thehandling area module 702 may receive information from the evaluationdevice 405 as to which handling areas 340 are presently manned by apharmacist (or other person) and which are idle, and/or the type ortypes of actions currently being performed by the pharmacist at thathandling area 340. When a handling area 340 is not manned by apharmacist, the handling area module 702 may make a determination not tosend the container 314 to that handling area 340.

The backlog module 704 may determine the currently workload of one ormore than one of the handling areas 340. For example, if more than onehandling area 340 is presently staffed by a pharmacist who is providingthe action with respect to a given container 314, the backlog module 704may determine the number of other containers 314 that are currentlyawaiting action at the relevant handling areas 340 so that the container314 may be distributed to a handling area 340 with a lower workload.

When the container 314 is set to receive pharmacist verification, theimage confirmation module 706 may access images taken within thepharmacy of the container 314 at one or more than one points during thependency of the container 314. Such images may be transmitted to theevaluation device 405 at the appropriate handling area 340 for use bythe pharmacist during the verification process.

The robot module 708 may operate the robot 320 to selectively pick thecontainer 314 from the handling area 312. The robot module 708 maycommunicate with the handling area status module 702 and/or the backlogmodule 704, for example, in order to determine a lane 342 into which thecontainer 314 is to be placed in order to queue the container 314 foraction by a pharmacist at an appropriate handling area 340.

FIG. 8 illustrates a method 800 for checking and exception handling,according to an example embodiment. The method 800 may be performed inthe check and exception center 300 as instructed by the control unit302, or may be otherwise performed.

At block 805, as the container 314 enters the distribution area 304, therobot 320 may pick the container 314 and scan the label of the container314 via the scanner 322. At decision point 810, a check may be made todetermine if the scan was successful, or if the label could not be read.If the label could not be read, the container 314 may be deemed anexception and the method may advance to block 815, discussed in detailbelow. However, if the label is readable, the information obtained bythe scanner 322 may then be sent to the communication module 602, and atblock 815, the identification module 604 may determine the type ofaction needed by the container 314. If the container 314 is anexception, the method 800 advances to block 815 in which the handlingarea status module 702 may determine which of the handling areas 340 areenabled for exception handling. However, at decision point 820, if thecontents of container 314 are to be counted, the method 800 advances toblock 825 in which the handling area status module 702 may determinewhich of the handling areas 340 are enabled for pill counting. In someembodiments, at decision point 820, if the contents of container 314 areto be checked by a pharmacist, the method 800 advances to block 830 inwhich the handling area status module 702 may determine which of thehandling areas 340 are enabled for pharmacist check.

The method 800 may advance to decision point 835 at which point adetermination may be made as to whether one or more than one handlingarea 340 is appropriate. Where only a single handling area 340 isappropriate, at block 840, the robot module 708 may instruct robot 320to place the container 314 into the lane 342 associated with thathandling area 340.

However, it may be determined that more than one handling area 340 isassociated with the type of action to be taken on the container 314 atblock 835. For example, multiple pharmacists may be working on therelevant task at more than one handling area 340. At block 845, theresource management subsystem 504 may utilize the backlog module 704 todetermine which handling area 340 will receive the container 314. Atblock 850, the robot module 708 instructs the robot 320 to place thecontainer 314 into the selected lane 342 for delivery to the technicianat the selected handling area 340.

FIG. 9 shows a block diagram of a machine in the example form of acomputer system 900 within which a set of instructions may be executedcausing the machine to perform any one or more of the methods,processes, operations, or methodologies discussed herein. The devices102, 106, 122-144 may include the functionality of the one or morecomputer systems 900.

In an example embodiment, the machine operates as a standalone device ormay be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a server computer, a client computer, a personal computer(PC), a tablet PC, a gaming device, a set-top box (STB), a PersonalDigital Assistant (PDA), a cellular telephone, a web appliance, anetwork router, switch or bridge, or any machine capable of executing aset of instructions (sequential or otherwise) that specify actions to betaken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The example computer system 900 includes a processor 902 (e.g., acentral processing unit (CPU) a graphics processing unit (GPU) or both),a main memory 904 and a static memory 906, which communicate with eachother via a bus 908. The computer system 900 further includes a videodisplay unit 910 (e.g., a liquid crystal display (LCD) or a cathode raytube (CRT)). The computer system 900 also includes an alphanumeric inputdevice 912 (e.g., a keyboard), a cursor control device 914 (e.g., amouse), a drive unit 916, a signal generation device 918 (e.g., aspeaker) and a network interface device 920.

The drive unit 916 includes a computer-readable medium 922 on which isstored one or more sets of instructions (e.g., software 924) embodyingany one or more of the methodologies or functions described herein. Thesoftware 924 may also reside, completely or at least partially, withinthe main memory 904 and/or within the processor 902 during executionthereof by the computer system 900, the main memory 904 and theprocessor 902 also constituting computer-readable media.

The software 924 may further be transmitted or received over a network926 via the network interface device 920.

While the computer-readable medium 922 is shown in an example embodimentto be a single medium, the term “computer-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “computer-readablemedium” shall also be taken to include any medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of themethodologies of the present invention. The term “computer-readablemedium” shall accordingly be taken to include, but not be limited to,solid-state memories, and optical media, and magnetic media. In someembodiments, the computer-readable medium is a non-transitorycomputer-readable medium.

The term “based on” or using, as used herein, reflects an open-endedterm that can reflect others elements beyond those explicitly recited.

Certain systems, apparatus, applications or processes are describedherein as including a number of modules. A module may be a unit ofdistinct functionality that may be presented in software, hardware, orcombinations thereof. When the functionality of a module is performed inany part through software, the module includes a computer-readablemedium. The modules may be regarded as being communicatively coupled.

The inventive subject matter may be represented in a variety ofdifferent embodiments of which there are many possible permutations.

In an example embodiment, a system is provided with a holding area, adistribution section and a manual section. The holding area is adaptedto hold containers awaiting action. The distribution section is adjacentthe holding section and has a robot adapted to select and pickcontainers from the holding section. The robot is disposed to distributethe container. The manual section is disposed adjacent the conveyor. Themanual section is adapted for inspection of the container.

The present disclosure makes reference to a robot and words of similarimport. A robot can be a machine capable of carrying out a complexseries of actions automatically. These complex series of actions mayinclude picking up, orientating, positioning and/or releasing acontainer or other structure. The robot may be dedicated to a singleseries of movements or may be able to execute multiple series ofmovements. A robot may include a processor that received instructionsand then executes instructions to control its movement. In anotherexample, a robot may resemble a human being and replicate certain humanmovements and functions, e.g., a robot may move location, have anarticulated arm, have grasping structures that replicate like fingersand do not damage containers, and the like.

Thus, methods and systems for operation of a check/exception stationhave been described. Although embodiments of the present invention havebeen described with reference to specific example embodiments, it willbe evident that various modifications and changes may be made to theseembodiments without departing from the broader spirit and scope of theembodiments of the invention. Accordingly, the specification anddrawings are to be regarded in an illustrative rather than a restrictivesense.

The methods described herein do not have to be executed in the orderdescribed, or in any particular order. Moreover, various activitiesdescribed with respect to the methods identified herein can be executedin serial or parallel fashion. Although “End” blocks are shown in theflowcharts, the methods may be performed continuously.

In the foregoing Detailed Description, it can be seen that variousfeatures are grouped together in a single embodiment for the purpose ofstreamlining the disclosure. This method of disclosure is not to beinterpreted as reflecting an intention that the claimed embodimentsrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive subject matter may lie inless than all features of a single disclosed embodiment. Thus, thefollowing claims are hereby incorporated into the Detailed Description,with each claim standing on its own as a separate embodiment.

1. A system comprising: a holding area; a manual section, wherein themanual section includes a plurality of handling areas each enabled forpill counting, pharmacist verification, exception handling, orcombinations thereof; a distribution section disposed proximate themanual section, the distribution section including a robot and ascanner, wherein the robot is adapted to pick a container from theholding area and to move the container to the scanner for scanning;wherein the robot is further adapted to direct the container to a firsthandling area of the plurality of handling areas, wherein at least onehandling area of the plurality of handling areas includes an evaluationdevice, and wherein the evaluation device configured to: determine asecond handling area being enabled for a determined action with respectto the container, determine workloads of the first handling area and thesecond handling area; and select a handling area from the first handlingarea and the second handling area with a lower workload to receive thecontainer.
 2. The system of claim 1, further comprising: at least oneconveyor to enable transportation of a container between thedistribution section and the manual section; a guiderail positioned soas to define a lane on the at least one conveyor, wherein the lane leadsto one of the plurality of handling areas.
 3. The system of claim 2,further comprising: an additional conveyor to enable transportation ofat least one container between the distribution section and the manualsection; wherein: the at least one conveyor extends between the firsthandling area and the distribution section; and the additional conveyorextends between the second handling area and the distribution section.4. The system of claim 2, further comprising: a feed conveyor to feedcontainers to the plurality of holding areas, wherein the feed conveyoris reachable by the robot.
 5. The system of claim 1, further comprising:the distribution section is further configured to determine whether thescanned container requires exception handling and to generate a thirdcommand to send the scanned container to a third handling area of theplurality of holding areas associated with exception handling based onthe determination.
 6. The system of claim 5, wherein the third commandto send the scanned container to the third handling area of theplurality of holding areas associated with the exception handling whenthe determination comprises at least one of the following: the containerhaving an unreadable label; the container having a defect; and thecontainer associated with a cancelled prescription order.
 7. The systemof claim 1, wherein the evaluation device is configured to allow apharmacist to enable at least one of the plurality of handling areas forpill counting, pharmacist verification, exception handling, orcombinations thereof.
 8. The system of claim 1, wherein the evaluationdevice is configured to provide a pharmacist operating one of theplurality of handling areas with information relating to the containerduring evaluation.
 9. The system of claim 1, wherein at least one of theplurality of handling areas includes a pill counter.
 10. The system ofclaim 1, further comprising a processor configured to: determine whetherthe scanned container requires pharmacist verification, determinewhether the scanned container requires pill counting, generate a firstcommand to send the scanned container to the first handling area of theplurality of handling areas associated with pharmacist verificationbased on the determination that the scanned container requirespharmacist verification, and generate a second command to send thescanned container to the second handling area of the plurality ofhandling areas associated with pill counting based on the determinationthat the scanned container requires pill counting.
 11. The system ofclaim 8, wherein the distribution section is further configured to causethe evaluation device to provide the pharmacist with the informationrelating to the container being evaluated.
 12. A method comprising:enabling a plurality of handling areas for a plurality of availableactions via an evaluation device, wherein the available action includespill counting, pharmacist verification, and exception handling;selecting a container from a holding area; scanning the container via ascanner; determining an action among the available actions to be takenwith respect to the container by the evaluation device, whereindetermining an action among the available actions includes determiningwhether the scanned container requires pharmacist verification, or thescanned container requires pill counting and generates a command basedon the determination; determining that a first handling area of theplurality of handling areas is enabled for a determined action withrespect to the container by the evaluation device; determining by theevaluation device that a second handling area is enabled for thedetermined action with respect to the container; determining workloadsof the first handling area and the second handling area by theevaluation device; and selecting the handling area with a lower workloadto receive the container by the evaluation device.
 13. The method ofclaim 12, further comprising: placing the container on a conveyorleading to the one of the plurality of handling areas.
 14. The method ofclaim 13, further comprising: picking a container from a holding area,via a robot, for scanning, wherein the robot places the container on theconveyor leading to the first handling area.
 15. The method of claim 14,further comprising: performing the determined action to the container atthe first handling area; transporting the container from the firsthandling area to the robot once the determined action has beencompleted; picking the container; re-scanning the container; determiningwhether any additional actions are to be taken with respect to thecontainer; when no additional actions are to be taken, placing thecontainer on an outbound conveyor; and where an additional action is tobe taken, determining that one of the plurality of handling areas isenabled for the additional action with respect to the container andplacing the container on a conveyor leading to the one of the pluralityof handling areas.
 16. The method of claim 12, further comprising:performing the determined action to the container at the first handlingarea; and transporting the container from the first handling area to theholding area once the determined action has been completed.
 17. Themethod of claim 16, further comprising: providing information relatingto the container to an evaluation device of the first handling area. 18.The method of claim 12, further comprising: flagging the container foran exception handling action based on at least one of the followingdeterminations: the container having an unreadable label; the containerhaving a defect; and the container associated with a cancelledprescription order.
 19. The method of claim 12, wherein determining theaction among the available actions includes determining whether thescanned container require exception handling.